Business Process: 3.3.6.2 Start Premise Based Service for Landlord - Tenant
Sibling Processes: 3.3.2.1 Start Premise Based Service, 3.3.2.3 Stop Premise Based Service, 3.3.2.2 Start Non-Premise Based Service, 3.3.2.4 Stop Non-Premise Based Service, 3.3.6.3 Stop Premise Based Service for Landlord - Tenant, 3.3.3.2 Determine Customer Deposit, 3.3.1.1 Establish Person and/or Account, 3.4.1.1 Manage Customer Contacts, 5.3.2.1 Manage Field Activities and Field Orders, 3.4.4.1a Enrollment in Budget, 3.4.4.1b Enrollment in Non-Billed Budget, 4.3.2.1 Manage Collection Process, 5.1.5.1 Manage Metered Site
This process describes the Start process for Premise based service for when a landlord is responsible for the property between tenants, or when the Service is transferring from tenant to tenant.
When a landlord is associated with a property and would like to have service reverted when a tenant moves out, a contract called a Landlord Agreement is established in the system. The Landlord can indicate preferences for each type of service provided at the property. The landlord can choose to have seasonal preferences. It is possible some services may not revert at all depending on the landlord's preferences.
Based on configured business rules the system uses the information defined on landlord agreement to create a Service Agreement(s) for the landlord when service for an existing tenant is stopped.
Many organizations need to group and manage multi-unit properties quickly and effectively. The organization can make use of Premise Management functionality to assist with large multi unit properties. If configured, Premise Management functionality can facilitate grouping of Premises together under a defined single premise called a Parent Premise. It can provide for a single view of properties for a landlord, including status of service. Premise Management functionality provides the ability to change landlord or service status for a group of premises at the same time in one transaction.